Autonomous configuration system for a service infrastructure

ABSTRACT

Various methods and systems for implementing an autonomous configuration system for configuring a service infrastructure are provided. An autonomous configuration system implements a service infrastructure configuration manager to identify discovered configuration data. The discovered configuration data supports circumventing a routing protocol for service infrastructure communications via an edge infrastructure, such that, the service infrastructure is alternatively configured to access remote configuration data based on the discovered configuration data. The discovered configuration data is discovered based an autonomous discovery service (e.g., sniffing service or a casting service). An initial configuration state is configured in the service infrastructure, based on the discovered configuration data. The service infrastructure can communicate with a service provider infrastructure associated with the service infrastructure to access the remote configuration data. The service infrastructure configuration manager accesses the remote configuration data and uses the remote configuration data to configure a final configuration state in the service infrastructure.

BACKGROUND

Large-scale networked systems are commonplace platforms employed in avariety of settings for running applications and maintaining data forbusiness and operational functions. For instance, a datacenter (e.g.,physical cloud computing platform) may provide a variety of services(e.g., web applications, email services, search engine services, etc.)for a plurality of customers simultaneously. These large-scale networkedsystems typically include a large number of resources distributedthroughout the data center or throughout multiple datacenters in aregion or multiple regions across the globe. Resources can resemble aphysical machine or a virtual machine (VM) running on a physical node orhost. The datacenter runs on hardware (e.g., power supplies, racks, andNetwork Interface Controllers (NIC)) and software components(Applications, Application Programming Interfaces (APIs), SQL Databases)that rely on each other to operate. In this regard, datacenters providehousing for computing systems and associated components—collectivelyreferred to as an infrastructure or service infrastructure. The serviceinfrastructure can support compute and storage operations for a varietyof compute workloads and operations. The service infrastructure can beinstalled in datacenters that are wholly-owned and operated by a serviceprovider or entity and also in datacenters not wholly-owned or operatedby the service provider. A service provider may refer to the latterdatacenter as an edge datacenter or edge infrastructure. In either case,a service infrastructure has to be properly provisioned and configuredin order to operate to support different services. As such, processes tosupport service infrastructure provisioning are integral to thedeployment of service infrastructures to datacenters.

SUMMARY

Embodiments described herein provide methods and systems forimplementing an autonomous configuration system for configuring serviceinfrastructures. A service infrastructure includes computing systems andassociated components—hardware and software—that support compute andstorage operations from a datacenter where the service infrastructure isdeployed. At a high level, an autonomous configuration system implementsa service infrastructure configuration manager to identify discoveredconfiguration data or utilize casting configuration data for a serviceinfrastructure. The discovered configuration data or the castingconfiguration data supports circumventing a routing protocol for serviceinfrastructure communications via an edge infrastructure. The serviceinfrastructure is alternatively configured based on the discoveredconfiguration data or the casting configuration data to access remoteconfiguration data at a service provider infrastructure to configure theservice infrastructure.

The discovered configuration data is discovered based on an autonomousdiscovery service (e.g., sniffing service) that leverages a waitingstate of the edge infrastructure and a pre-configured state of theservice infrastructure to identify the discovered configuration data.The casting configuration data is utilized based on an autonomouscasting service (e.g., casting service) that leverages a casting IPaddress to peer the service infrastructure with the edge infrastructure,making the service infrastructure internet accessible. Based on thediscovered configuration data or the casting configuration data, aninitial configuration state is configured in the service infrastructure.The service infrastructure can then communicate with a service providerinfrastructure associated with the service infrastructure to access theremote configuration data. The service infrastructure configurationmanager accesses the remote configuration data from the service providerinfrastructure and uses the remote configuration data to configure afinal configuration state in the service infrastructure.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used in isolation as an aid in determining the scope of the claimedsubject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary distributed computinginfrastructure and autonomous configuration system, in accordance withembodiments described herein;

FIG. 2 is a block diagram of an exemplary distributed computinginfrastructure and autonomous configuration system, in accordance withembodiments described herein;

FIG. 3 is a flow diagram showing an exemplary method for providing anautonomous configuration system, in accordance with embodimentsdescribed herein;

FIG. 4 is a flow diagram showing an exemplary method for providing anautonomous configuration system based on a sniffing service, inaccordance with embodiments described herein;

FIG. 5 is a flow diagram showing an exemplary method for providing anautonomous configuration system based on a casting service, inaccordance with embodiments described herein;

FIG. 6 is a block diagram of an exemplary computing environment suitablefor use in implementing embodiments described herein; and

FIG. 7 is a block diagram of an exemplary computing environment suitablefor use in implementing embodiments described herein.

DETAILED DESCRIPTION

Datacenters can provide housing for computing systems and associatedcomponents—collectively referred to as an infrastructure or serviceinfrastructure. The service infrastructure can support compute andstorage operations for a variety of compute workloads and operations.The service infrastructure can be installed in datacenters that arewholly-owned and operated by a service provider or entity and also indatacenters not wholly-owned or operated by the service provider. Aservice provider may refer to the latter datacenter as an edgedatacenter or edge infrastructure. In either case, a serviceinfrastructure has to be properly provisioned and configured in order tooperate to support different services. For example, a serviceinfrastructure has to be configured with location-specific networkconfiguration to operate correctly.

Service infrastructure that is to be deployed into a datacenter oftendoes not have the network configuration of the datacenter where theservice infrastructure is to be installed. For example, a top-of-rackswitch (TOR) lacks the network configuration of the datacenter toconnect to the edge infrastructure to access datacenter resources orexternal resources. Access to the datacenter network supportsaccessibility of the service infrastructure to datacenter resources andexternal resources. With network access, a service infrastructure cancommunicate with a service provider infrastructure to receiveconfiguration data. As such, the service infrastructure has to beconfigured to connect to the datacenter network and to have access tothe datacenter resources and external resources.

Conventional methods for configuring a service infrastructure in adatacenter have several shortcomings because of the resource-intensiveprocesses involved in configuring service infrastructures indatacenters. For example, a TOR switch requires manual configuration ofthe service infrastructure with significant human intervention, whichcan be time consuming, inefficient, and susceptible to human error. Inone exemplary implementation, an alternate channel to the TOR switch canbe configured by an operator to access and configure the TOR switch tocommunicate with the service provider infrastructure. The alternatechannel can be configured using an additional network card, a server(e.g., blade server) with a configuration OS, and an operator accessingthe server to configure the TOR. In addition, a datacenter that is notwholly-owned by a cloud service provider lacks pre-existingadministrator infrastructure that could facilitate configuration of aservice infrastructure.

Another exemplary implementation might include allowing the edgeinfrastructure provider to have access to configuration information of aservice provider using the edge infrastructure; however, theconfiguration information is confidential and sharing such confidentialinformation can open the service provider to unnecessary risk. Othervariations and combinations of shortcomings exist with conventionalmethods for configuring a service infrastructure. As such, processes tosupport service infrastructure provisioning are integral to thedeployment of service infrastructures to datacenters.

Embodiments described herein provide simple and efficient methods andsystems for implementing autonomous configuration system for serviceinfrastructures. A service infrastructure includes computing systems andassociated components—hardware and software—that support compute andstorage operations from a datacenter where the service infrastructure isdeployed. As an initial matter, a service infrastructure is shipped tothe edge datacenter. The service infrastructure, for purposes ofproviding a detailed description, is a service infrastructure maintainedin a rack. The rack includes a standard frame for mounting equipmentincludes blades (i.e., modularized server computer), power and networkcomponents. The rack can specifically include a switch (e.g., a top ofrack switch or TOR switch). The service infrastructure rack is installed(e.g., connecting power and network cables) at the edge datacenter basedon service provider specifications. The edge datacenter includes an edgeinfrastructure that includes a network device (e.g., edge infrastructureswitch) that supports connecting the service infrastructure to the edgeinfrastructure. The service infrastructure is associated with a serviceprovider that manages the service infrastructure and the edgeinfrastructure is associated with an edge infrastructure provider thatmanages the edge infrastructure.

At a high level, the autonomous configuration system supports amechanism for a service provider to configure a service infrastructurein a datacenter. In particular, the service provider can have theirservice infrastructure automatically and autonomously configured in anedge datacenter or edge infrastructure that is not owned and/orcontrolled by the service provider. The autonomous configuration systemmay operate based on a service infrastructure (e.g., serviceinfrastructure configuration manager) of the autonomous configurationsystem automatically discovering at least a portion of the serviceinfrastructure configuration data (e.g., discovered configuration data)or automatically utilizing casting configuration data (e.g., a castingIP address) and configuring the service infrastructure (e.g., initialconfiguration state) based on the discovered configuration data or thecasting configuration data. The discovered configuration data can beidentified based on the edge infrastructure (e.g., edge infrastructureconfiguration manager or switch) that is configured for a routingprotocol. The casting configuration data can be utilized based on acasting IP address from the service infrastructure provider (e.g., ananycast IP address utilized by the casting service or switch). The edgeinfrastructure, in either case, maintains the routing protocolconfiguration data for configuring the service infrastructure. The edgeinfrastructure configuration manager maintaining the routing protocolconfiguration data may include the edge infrastructure (e.g., a switch)configured based on the routing protocol configuration data. The edgeinfrastructure can also store a portion of a service infrastructureportion of the routing protocol configuration data, where the routingprotocol configuration data allows a switch of the serviceinfrastructure to communicate with a switch of the edge infrastructurebased on the routing protocol.

By way of background, the edge infrastructure may operate based on apredefined routing protocol (e.g., Border Gateway Protocol) associatedwith the routing protocol configuration data. A fully finally configuredservice infrastructure, at an edge datacenter, also operates with theedge infrastructure based on the routing protocol. The routing protocolrefers to an exterior gateway protocol for routing information betweensystems (e.g., autonomous networks or service providers) on theinternet. The routing protocol makes routing decisions on paths, networkpolicies, or rule-sets defined for reachability between systems. Assuch, by way of example, a BGP link, in a fully finally configuredservice infrastructure, exists between a switch of the serviceinfrastructure and a switch of the edge infrastructure. In this regard,routing protocol configuration data can refer to edge infrastructureconfiguration data and service infrastructure configuration data thatsupport BGP and a link between the edge infrastructure and serviceinfrastructure using BGP. The edge infrastructure switch can beconfigured with the edge infrastructure configuration data. The edgeinfrastructure may be preconfigured (e.g., a waiting state andperforming waiting state operations) to communicate with the serviceinfrastructure using the routing protocol; however, with embodimentsdescribed herein, the edge infrastructure and routing protocol areexploited or circumvented (e.g., via an autonomous discovery service oran autonomous casting service) to identify the discovered configurationdata or utilize the casting configuration data, respectively, instead.

The discovered configuration data from the autonomous discoveringservice (e.g., sniffing service) or the casting configuration data fromthe autonomous casting service allows the service infrastructure to bepartially provisioned (e.g., initial configuration state). The serviceinfrastructure can then communicate with a service providerinfrastructure (e.g., service provider cluster) to access provisioningdata (e.g., remote configuration data). The service providerinfrastructure can communicate provisioning data to the serviceinfrastructure at the edge datacenter. The remote configuration dataallows the service infrastructure to be fully provisioned (e.g., finalconfiguration state). The autonomous configuration system configures theservice infrastructure based on an autonomous configuration frameworkthat includes the initial configuration state and the finalconfiguration state, and in embodiments, an intermediate configurationstate for security purposes. The intermediate configuration stateincludes the service infrastructure being provisioned using anincremental provisioning process based at least in part on securitychecks that have to be met as part of the incremental provisioningprocess, as described herein in more detail.

In operation, the autonomous configuration system can support twodifferent types of implementations: an autonomous discovery service andan autonomous casting service corresponding to a sniffing-based processand a casting-based process, respectively. A service infrastructureconfiguration manager can support either one or both of the autonomousconfiguration implementations based on a sniffing service and a castingservice, respectively.

With reference to the sniffing-based process, the sniffing-based processsupports configuration of the service infrastructure based on apacket-sniffing methodology that allows the service infrastructure toinspect traffic packets from the edge infrastructure to identify serviceinfrastructure configuration data (e.g., discovered configuration data).The discovered configuration data is used to configure the serviceinfrastructure. The sniffing-based process utilizes the edgeinfrastructure announcements of the edge infrastructure's presence toidentify the discovered configuration data and circumvent, at leasttemporarily, direct configuration over the routing protocol.

The sniffing-based process can be described in more detail by way ofexample, which is not meant to be limiting. The sniffing-based processleverages the edge infrastructure's (e.g., edge infrastructureconfiguration manager or switch) actions, when the edge infrastructureis configured with the routing protocol configuration data, to identifyportions of a service infrastructure configuration data (i.e.,discovered configuration data). The edge infrastructure (e.g., switch)can be configured in a waiting state (e.g., a BGP-based state) thatincludes initiating and performing neighbor discovery operations (e.g.,Internet Control Message Protocol—ICMPv6 Neighbor Discovery requests andAddress Resolution Protocol—ARP requests). In an exemplaryimplementation, the waiting state can support IPv4 or IPv6 configurationof the service infrastructure and further includes reserving IPaddresses (e.g., at least 2 IP addresses—one each for the edgeinfrastructure and the service infrastructure TOR). The edgeinfrastructure, in its waiting state, periodically sends out datapackets and listens for a response from an expected serviceinfrastructure for direct configuration over the routing protocol.Basically, the edge infrastructure is anticipating to discover who(e.g., a switch) to communicate with from the service infrastructure.However, without any manual intervention, the service infrastructure(e.g., service configuration manager or server) monitors data trafficand inspects the data packets to discover and extract at least portions(e.g., discovered configuration data) of the service infrastructureconfiguration data. The service infrastructure can be in apre-configuration state that allows the service infrastructure tomonitor data traffic. For example, the service infrastructure TOR switchmay be configured in a transparent state to forward all traffic to aserver on the rack, where the server includes the service infrastructureconfiguration manager that supports identifying the discoveredconfiguration data. The discovered configuration data (e.g., a reservedIP address for the server) can be used to autonomously configure (e.g.,initial configuration state) the service infrastructure.

Autonomous configuration includes initializing the serviceinfrastructure into an initial configuration state. In particular,during an initial configuration state, the service infrastructureconfiguration manager communicates with a service providerinfrastructure via the edge infrastructure while bypassing configurationof the TOR switch with routing protocol configuration data. The reservedIP address for the service infrastructure is an internet accessible IPaddress which the edge infrastructure trusts that any device using theIP address is allowed access to the internet based on the IP address.The initial configuration state includes the service infrastructureconfiguration manager accessing the service provider infrastructure toretrieve remote configuration data, as described herein in more detail.

With reference to the casting-based process, the casting-based processsupports configuration of the service infrastructure based on a networkaddressing and routing methodology (e.g., anycast) that allows a serviceinfrastructure to be accessible, via an edge infrastructure, by theservice infrastructure provider using casting configuration data (e.g.,any cast, casting IP address, etc.). The casting configuration data isused to configure the service infrastructure and a casting IP address ofthe casting configuration data is utilized by the service infrastructureto peer with the edge infrastructure. Peering can refer to creating aninterconnection between separate networks to exchange traffic. Thecasting-based process utilizes the edge infrastructure peered with theservice infrastructure based on the casting IP address to provide theservice infrastructure with internet accessibility. With internetaccessibility, the service infrastructure broadcasts the casting IPaddress, such that, the service provider infrastructure can communicatewith the service infrastructure to circumvent, at least temporarily,direct configuration over the routing protocol.

The casting-based process can be described in more detail by way ofexample, which is not meant to be limiting. The casting-based processleverages casting configuration data (e.g., casting IP address) and acasting service to configure the service infrastructure (e.g., a TORswitch) with a casting IP address (e.g., anycast IP address). Forexample, the service infrastructure can be in a pre-configuration state,where the service infrastructure is configured with the anycast IPaddress. The anycast IP address supports the peering with the edgeinfrastructure based on the anycast IP address. The edge infrastructureis in a waiting state until the anycast IP address is used to peer withthe edge infrastructure with the service infrastructure. In an exemplaryimplementation, the casting IP address (or casting IP address range)allows routing of data between nearest devices that have the samecasting IP address configuration and then the edge infrastructure isthen peered with the service infrastructure. In particular, the edgeinfrastructure peers with the service infrastructure using the anycastIP address. The service infrastructure is internet accessible via theedge infrastructure and can broadcast based on the anycast IP addressand internet accessibility.

Autonomous configuration includes initializing the serviceinfrastructure into an initial configuration state. The casting-basedprocess leverages peering of a service infrastructure and an edgeinfrastructure to configure an initial configuration state (e.g., peeredwith the edge infrastructure and internet accessibility) in the serviceinfrastructure. The service infrastructure in the initial configurationstate further includes the service infrastructure broadcasting via theinternet with anycast IP address, which a service providerinfrastructure can utilize to configure the service infrastructure. Inthe initial configuration state, the edge infrastructure can receivecommunications from a service provider infrastructure via the anycast IPaddress. The service provider infrastructure (e.g., a predefined remoteconfiguration data location) communicates to the service infrastructurein response to the broadcasting via the casting IP address forprovisioning. In this regard, the edge infrastructure and the serviceinfrastructure circumvent direct configuration using the routingprotocol. The service provider infrastructure (that includesprovisioning manager and remote configuration data) can now reach theservice infrastructure via the anycast IP address. In particular, theservice provider infrastructure can reach the TOR switch without humanintervention to configure the TOR switch and the service infrastructurewith the remote configuration data, as described herein in more detail.

The service infrastructure can be configured with remote configurationdata. The remote configuration data can be provided from the serviceprovider infrastructure (e.g., a cluster) to further configure theservice infrastructure. Remote configuration data can refer to differenttypes of computing configurations and settings for the serviceinfrastructure such that the service infrastructure can operateappropriately and provide access to technology resources. Remoteconfiguration data can also allow a service provider to manage theservice infrastructure. The remote configuration data can includehardware and software configurations for the service infrastructure. Forexample, the remote configuration data can include networkconfigurations that support intra-rack and extra-rack communications.Other types of variations and combinations of remote configuration dataare contemplated with embodiments of the present disclosure.

The autonomous configuration system configures the serviceinfrastructure based on an autonomous configuration framework thatincludes the initial configuration state and the final configurationstate, and in embodiments, an intermediate configuration state forsecurity purposes. The intermediate configuration state includes theservice infrastructure being provisioned using an incrementalprovisioning process based at least in part on security checks that haveto be met as part of the incremental provisioning process. Theincremental provisioning processing operates to establish a trustbetween the service infrastructure and the service providerinfrastructure (e.g., via an intermediate service providerinfrastructure having intermediate remote configuration data). Theintermediate remote configuration data can be communicated to serviceinfrastructure in the initial configuration state where the intermediateremote configuration data is used to initialize an intermediateconfiguration state (e.g., trust establishing state).

The intermediate configuration state can be based on any variations andcombinations of trusted computing (e.g., endorsement key, memorycurtaining, sealed storage, remote attestation, trusted third party,etc.) used to support communications between service infrastructure andthe service provider infrastructure. After a trust has been establishedduring the trust establishing state, then further communications canoccur with the primary service infrastructure having primary remoteconfiguration data. The primary remote configuration data can then becommunicated to the service infrastructure such that the serviceinfrastructure can be configured in a final configuration state.

As such, autonomous configuration of a service infrastructure in an edgedatacenter can be achieved based on circumventing direct configurationusing routing protocol configuration data and relying on an autonomousdiscovery services (e.g., sniff service or casting service) thatidentify discovered configuration data for an initial configuration ofthe service infrastructure to access remote configuration data for afinal configuration of the service infrastructure.

With reference to FIG. 1, embodiments of the present disclosure can bediscussed with reference to an exemplary distributed computingenvironment that is an operating environment for implementingfunctionality described herein of an autonomous configuration system100. The autonomous configuration system 100 includes an edge datacenter110 having an edge infrastructure 120 and an edge infrastructureconfiguration manager 122. The edge datacenter 110 also includes aservice infrastructure 130 having a service infrastructure configurationmanager 132. The service infrastructure configuration manager 132 canoperate an autonomous discovery service 134. The autonomousconfiguration system 100 further includes a service providerinfrastructure 150 having a provisioning manager 160 having remoteconfiguration data 162. The components of the autonomous configurationsystem 100 may communicate with each other via a network 140, which mayinclude, without limitation, one or more local area networks (LANs)and/or wide area networks (WANs). Such networking environments arecommonplace in offices, enterprise-wide computer networks, intranets,and the Internet.

The autonomous configuration system 100 in an alternative embodiment isillustrated in FIG. 2. FIG. 2 includes corresponding components shown inFIG. 1 with additional components supporting functionality of theautonomous configuration system. FIG. 2 includes the edge datacenter110, the edge infrastructure 120, switch 120A, edge infrastructureconfiguration manager 122 and service infrastructure having a switch130A and server 130B (e.g., blade on the rack) running the serviceinfrastructure configuration manager 132. The service infrastructureconfiguration manager 132 can operate a sniffing service 134A and/or acasting service 134B as described herein in more detail. FIG. 2 furtherincludes the service provider infrastructure 150 which, in one exemplaryembodiment, supports an incremental provisioning process for securitypurposes. The service provider infrastructure 150 includes anintermediate provisioning manager 160A having intermediate remoteconfiguration data 162A and a primary provisioning manager 160B havingprimary remote configuration data 162B.

A system, as used herein, refers to any device, process, or service orcombination thereof. A system may be implemented using components ashardware, software, firmware, a special-purpose device, or anycombination thereof. A system may be integrated into a single device orit may be distributed over multiple devices. The various components of asystem may be co-located or distributed. The system may be formed fromother systems and components thereof. It should be understood that thisand other arrangements described herein are set forth only as examples.

Having identified various components of the distributed computingenvironment, it is noted that any number of components may be employedto achieve the desired functionality within the scope of the presentdisclosure. The various components of FIG. 1 and FIG. 2 are shown withlines for the sake of clarity. Further, although some components of FIG.1 and FIG. 2 are depicted as single components, the depictions areexemplary in nature and in number and are not to be construed aslimiting for all implementations of the present disclosure. Theautonomous configuration system 100 functionality can be furtherdescribed based on the functionality and features of the above-listedcomponents.

Other arrangements and elements (e.g., machines, interfaces, functions,orders, and groupings of functions, etc.) can be used in addition to orinstead of those shown, and some elements may be omitted altogether.Further, many of the elements described herein are functional entitiesthat may be implemented as discrete or distributed components or inconjunction with other components, and in any suitable combination andlocation. Various functions described herein as being performed by oneor more entities may be carried out by hardware, firmware, and/orsoftware. For instance, various functions may be carried out by aprocessor executing instructions stored in memory.

With continued reference to FIG. 2, FIG. 2 includes the edge datacenter110 that supports running hardware (e.g., power supplies, racks, andNetwork Interface Controllers (NIC)) and software components(Applications, Application Programming Interfaces (APIs), SQL Databases)that rely on each other to operate. The edge datacenter 110 provideshousing for computing systems and associated components—collectivelyreferred to as edge infrastructure or a service infrastructure whenprovided via a service provider that does not own and control the edgedatacenter 110. The edge datacenter can specifically provide networkaccess to the internet for service infrastructure (e.g., serviceinfrastructure 130) running in the edge datacenter 110. The edgedatacenter 110 through the edge infrastructure (e.g., edgeinfrastructure 120) supports configuring the service infrastructure 130to have access to the internet. For example, the edge infrastructure 120includes a network device (e.g., switch 120A) that links with theservice infrastructure 130 to reach other autonomous networks (e.g.,service provider infrastructure 150). In particular, a routing protocol(e.g., Border Gateway Protocol) can be configured on the switch 120A.When the edge infrastructure is linked over the routing protocol to theservice infrastructure 130 (e.g. switch 130A) the routing protocolsupports routing decisions for communications from the serviceinfrastructure 130 based on paths, network policies, or rule-setsconfigured for making routing decisions.

The switch 120A operates with the edge infrastructure configurationmanager 122 to support performing operations that provide thefunctionality of the switch 120A. The edge infrastructure configurationmanager configures switch 120A in a waiting state. With embodimentsdescribed herein, the switch 120A upon a final configuration state ofthe service infrastructure 130 eventually operates based on the routingprotocol; however, in order to implement autonomous configuration of theservice infrastructure 130, the routing protocol is circumvented basedon discovering configuration data (e.g., discovered configuration data)from the switch 120A while in the waiting state. The switch 120A is in awaiting state in that the switch has not been configured with a finalconfiguration operating using the routing protocol.

The waiting state of the switch 120A can operate with an autonomousdiscovery service or an autonomous casting service: a sniffing-basedprocess or a casting-based process. In the waiting state of the switch120A in the sniffing-based process, the switch 120A is configured basedon routing protocol configuration data and the switch 120A announces itspresence using neighbor discovery operations. The switch 120Aperiodically sends out data packets and listens for a response from theswitch 130A. In the waiting state of the switch 120A in thecasting-based process, the switch 120A is also configured based onrouting protocol configuration data and optionally (e.g., provided inadvance from the service infrastructure provider) a casting IP address.The switch 120A responds to an advertisement of the casting IP addressthen starts casting IP address-based operations. Conventionally, theswitch 130A can be configured manually and directly based on linking theswitch 130A with the switch 120A using the routing protocolconfiguration data. However, with embodiments of the present invention,configuring the switch 130A for the routing protocol is circumvented, atleast temporarily, to support automated configuration of the serviceinfrastructure.

With continued reference to FIG. 2, service infrastructure 130 includesthe switch 130A that can be configured in a final configuration state ofthe service infrastructure 130 to operate with the switch 120A using therouting protocol. The switch 130A in a pre-configuration state of theservice infrastructure 130 for an autonomous discovery service, theswitch 130A is configured to a transparent state where switch 130Aoperates to forward traffic received at the switch. The switch 130A canforward the data traffic to additional components (e.g., a server 130Brunning the service infrastructure configuration manager 132) in theservice infrastructure 130. During the pre-configuration state, theservice infrastructure configuration manager 132 can control operationsin the service infrastructure 130 based on traffic (e.g., data packets)forwarded from the switch 130A in the transparent state. In this regard,the switch 130A which would conventionally be configured to operate withthe switch 120A is, at least temporarily, bypassed for the serviceinfrastructure configuration manager 132 to begin autonomousconfiguration of the service infrastructure 130. The switch 130A in apre-configuration state of the service infrastructure 130 for anautonomous casting service can be configured with the casting IPaddress. The switch 130A alone or in combination with the castingservice can operate to perform casting IP based operations to beginpeering with the edge infrastructure 120. Other variations andcombinations of pre-configuration states are contemplated withembodiments of the present disclosure.

The service infrastructure configuration manager 132 runs on server 130Bto support autonomous configuration functionality. The serviceinfrastructure configuration manager 132 can implement autonomousdiscovery service or autonomous casting services. For example, asniffing service 134A that supports sniffing-based process forautonomous discovery or a casting service 134B that supports acasting-based process for autonomous configuration. The serviceinfrastructure configuration manager 132 can be initialized in apre-configuration state to support identifying discovered configurationdata for autonomous discovery or accessing configuration data (e.g.,casting IP address) for autonomous configuration. The discoveredconfiguration data is used to configure the service infrastructure foraccess to the service provider infrastructure. For example, during asniffing-based process the service infrastructure configuration managerlistens for packets communicated from the switch 120A and identifiesdiscovered configuration data. The discovered configuration data can be,for example, an IP address that is reserved and corresponds to a pairedIP address in the switch 120A such that the service infrastructure isprovided access to other autonomous networks.

In a casting-based process, the edge infrastructure 120 can beconfigured to listen for the presence of the casting IP address. In oneembodiment, the service infrastructure manager configures the switch130A based on the casting IP address such that the edge infrastructurecan peer with the service infrastructure via the switch. The casting IPaddress is provided from the service provider to the serviceinfrastructure to pre-configure the service infrastructure based on thecasting IP address. The casting IP address links the server 130B and/orswitch 130A to the switch 120A for access to the other autonomousnetworks (i.e., internet accessibility). In this regard, the serviceinfrastructure configuration manager 132 can be in a pre-configurationstate to access the casting configuration data to configure the serviceinfrastructure in an initial configuration state for access to theservice provider infrastructure and remote configuration data.

The service provider infrastructure 150 is configured to support aprovisioning manager (e.g., provisioning manager 160, intermediateprovisioning manager 160A and primary provisioning manager 160B) thatprovides remote configuration data (e.g., remote configuration data 162,intermediate remote configuration data 162A and primary remoteconfiguration data 162B). The provisioning manager supports aprovisioning process that allows the service infrastructure 130 toreceive remote configuration data such that the service infrastructure130 is configured to provide services of the service provider. Theservice infrastructure 130 can be configured to a final configurationthat allows the service infrastructure 130 to support compute andstorage operations for user accessing technology resources via theservice infrastructure 130. For example, users can be given access todata repositories or granted authorization to systems, networkapplications and databases based on appropriate credentials. The serviceinfrastructure final configuration, in particular, includes the switch130A communicating with switch 120A using a routing protocol to directcommunications from the service infrastructure 130. In this regard, theswitch 130A can be specifically reconfigured from the transparent statein to the final configuration state as part of the final configurationof the service infrastructure 130. Additional components of the serviceinfrastructure 130 are further fully provisioned using the remoteconfiguration data and processes defined for configuring the serviceinfrastructure 130.

As depicted in FIG. 2, the service provider infrastructure 150 caninclude an intermediate provisioning manager 160A and a primaryprovisioning manager 160B) that provides intermediate remoteconfiguration data 162A and primary remote configuration data 162B. Theautomated configuration system 100 supports an incremental provisioningprocess that provides increased security in the autonomous configurationsystem. The incremental provisioning processing operates with theintermediate provisioning manager 160A to establish a preliminary trustbetween the service infrastructure 130 and the intermediate provisioningmanager 160A. The intermediate provisioning manager 160A can communicatewith the service infrastructure in the initial configuration state wherethe intermediate remote configuration data 162A is used to initialize anintermediate configuration state (e.g., a trust establishing state) atthe service infrastructure. The trust establishing state can be based onany variations and combinations of trusted computing (e.g., endorsementkey, memory curtaining, sealed storage, remote attestation, trustedthird party, etc.) used to support communications between serviceinfrastructure 130 and the service provider infrastructure 150 as partof establishing trust with the service infrastructure 130. In oneexemplary embodiment, the service infrastructure establishes trust basedauthentication credentials (e.g., hardware or software basedauthentication credentials) communicated to the intermediateprovisioning manager 160A. In operation, after a trust has beenestablished then further communications can occur with the primaryprovisioning manager 160B having the primary remote configuration data162B. The primary remote configuration data 162B can then becommunicated to the service infrastructure 130 such that the serviceinfrastructure can be configured in a final configuration state asdiscussed above.

Turning now to FIG. 3, a flow diagram is provided that illustrates amethod 300 for providing autonomous configuration of serviceinfrastructures. The method 300 can be performed using the autonomousconfiguration system described herein. In particular, one or morecomputer storage media having computer-executable instructions embodiedthereon that, when executed, by one or more processors, can cause theone or more processors to perform the method 300. Initially at block310, discovered configuration data or casting configuration data isidentified or utilized, respectively, for a service infrastructure. Thediscovered configuration data or casting configuration data supports theservice infrastructure to circumvent a routing protocol. The serviceinfrastructure is alternatively configured to access remoteconfiguration data based on the discovered configuration data or thecasting configuration data, the discovered configuration data isdiscovered based on an autonomous discovery service and the castingconfiguration data is implemented based on an autonomous castingservice.

In a first embodiment, the autonomous discovery service is a sniffingservice, the sniffing service circumvents configuration of ananticipated switch of the service infrastructure and alternativelyidentifies the discovered configuration data based on monitoring datatraffic that includes at least one reserved IP address. Using theautonomous discovery service, the discovered configuration data isidentified from an edge infrastructure that operates in a waiting stateto configure, based on the routing protocol (e.g., routing protocolconfiguration data), the edge infrastructure to link with theanticipated switch of the service infrastructure. In a secondembodiment, the autonomous casting service is a casting service, thecasting service circumvents configuration of an anticipated switch ofthe service infrastructure and alternatively utilizes the castingconfiguration data that comprises a casting IP address.

At block 312, an initial configuration state is configured in theservice infrastructure, based on the discovered configuration data. Inthe initial configuration state, the service infrastructure cancommunicate with a service provider infrastructure associated with theservice infrastructure to access remote configuration data. At block314, a first portion of the remote configuration data is accessed fromthe service provider infrastructure, the first portion of the remoteconfiguration data is intermediate remote configuration data from anintermediate provisioning manager. The intermediate provisioning managerin a service provider infrastructure operates to communicateintermediate remote configuration data for implementing an incrementalprovisioning process. The intermediate remote configuration datasupports configuring the service infrastructure in the intermediateconfiguration state, the intermediate configuration state is a trustestablishing state between the service infrastructure and the serviceprovider infrastructure. At block 316, the intermediate configurationstate is configured in the service infrastructure using the intermediateremote configuration data.

At block 318, a second portion of the remote configuration data isaccessed from the service provider infrastructure. The second portion ofthe remote configuration data is primary remote configuration data froma primary provisioning manager. The primary provisioning manager in theservice infrastructure operates to communicate primary remoteconfiguration data for implementing the incremental provisioningprocess. The primary remote configuration data supports configuring theservice infrastructure in the final configuration state. The finalconfiguration state can include a switch of the edge infrastructure anda switch of service infrastructure communicating using the routingprotocol, the routing protocol was previously circumvented based on thediscovered configuration data. At block 320, the final configurationstate is configured in the service infrastructure using the primaryremote configuration data.

Turning now to FIG. 4, a flow diagram is provided that illustrates amethod 400 for providing autonomous configuration of serviceinfrastructures. The method 400 can be performed using the autonomousconfiguration system described herein. Initially at block 410,discovered configuration data is identified for a service infrastructurefrom an edge infrastructure in a waiting state comprising the edgeinfrastructure performing neighbor discovery operations. The discoveredconfiguration data supports the service infrastructure circumventing arouting protocol. The service infrastructure is alternatively configuredto access remote configuration data based on the discoveredconfiguration data, the discovered configuration data is discoveredbased on a sniffing service. The sniffing service circumventsconfiguration of the service infrastructure using the routing protocolto identify the discovered configuration data. The sniffing serviceidentifies the discovered configuration data based on monitoring datatraffic that comprises at least one reserved IP address. The sniffingservice operates with the service infrastructure in a pre-configurationstate comprising a switch of the service infrastructure in a transparentstate, the switch forwards monitored data traffic to a serviceinfrastructure configuration manager. At block 412, an initialconfiguration state is configured in the service infrastructure, basedon the discovered configuration data. The service infrastructure canthen communicate with the service provider infrastructure associatedwith the service infrastructure to access remote configuration data. Atblock 414, the remote configuration data is accessed from the serviceprovider infrastructure. At block 416, a final configuration state isconfigured in the service infrastructure.

Turning now to FIG. 5, a flow diagram is provided that illustrates amethod 500 for providing autonomous configuration of serviceinfrastructures. The method 500 can be performed using the autonomousconfiguration system described herein. Initially at block 510,discovered configuration data is identified for a service infrastructurefrom an edge infrastructure in a waiting state comprising the edgeinfrastructure performing casting IP address operations. The discoveredconfiguration data supports the service infrastructure circumventing arouting protocol. The service infrastructure is alternatively configuredto access remote configuration data based on the discoveredconfiguration data. The casting service circumvents configuration of theservice infrastructure using the routing protocol to identify thediscovered configuration data. The casting service identifies thediscovered configuration data based on monitoring data traffic thatcomprises a casting IP address. The casting service operates with theservice infrastructure in a pre-configuration state comprising a switchof the service infrastructure in a transparent state, the switchforwards monitored data traffic to a service infrastructureconfiguration manager. At block 512, an initial configuration state isconfigured in the service infrastructure, based on the discoveredconfiguration data. The service infrastructure can then communicate witha service provider infrastructure associated with the serviceinfrastructure to access remote configuration data. At block 514, theremote configuration data is accessed from the service providerinfrastructure. At block 516, a final configuration state is configuredin the service infrastructure.

With reference to the autonomous configuration system, embodimentsdescribed herein support automatic and autonomous configuration ofservice infrastructure. The autonomous configuration system componentsrefer to integrated components for autonomous configuration. Theintegrated components refer to the hardware architecture and softwareframework that support data access functionality using the autonomousconfiguration system. The hardware architecture refers to physicalcomponents and interrelationships thereof and the software frameworkrefers to software providing functionality that can be implemented withhardware embodied on a device. The end-to-end software-based autonomousconfiguration system can operate within the autonomous configurationsystem components to operate computer hardware to provide autonomousconfiguration system functionality. As such, the autonomousconfiguration system components can manage resources and provideservices for the autonomous configuration system functionality. Anyother variations and combinations thereof are contemplated withembodiments of the present invention.

By way of example, the autonomous configuration system can include anAPI library that includes specifications for routines, data structures,object classes, and variables may support the interaction between thehardware architecture of the device and the software framework of theautonomous configuration system. These APIs include configurationspecifications for the autonomous configuration system such that thedifferent components therein can communicate with each other in theautonomous configuration system, as described herein.

Having briefly described an overview of embodiments of the presentinvention, an exemplary operating environment in which embodiments ofthe present invention may be implemented is described below in order toprovide a general context for various aspects of the present invention.Referring initially to FIG. 6 in particular, an exemplary operatingenvironment for implementing embodiments of the present invention isshown and designated generally as computing device 600. Computing device600 is but one example of a suitable computing environment and is notintended to suggest any limitation as to the scope of use orfunctionality of the invention. Neither should the computing device 600be interpreted as having any dependency or requirement relating to anyone or combination of components illustrated.

The invention may be described in the general context of computer codeor machine-useable instructions, including computer-executableinstructions such as program modules, being executed by a computer orother machine, such as a personal data assistant or other handhelddevice. Generally, program modules including routines, programs,objects, components, data structures, etc. refer to code that performparticular tasks or implement particular abstract data types. Theinvention may be practiced in a variety of system configurations,including hand-held devices, consumer electronics, general-purposecomputers, more specialty computing devices, etc. The invention may alsobe practiced in distributed computing environments where tasks areperformed by remote-processing devices that are linked through acommunications network.

With reference to FIG. 6, computing device 600 includes a bus 610 thatdirectly or indirectly couples the following devices: memory 612, one ormore processors 614, one or more presentation components 616,input/output ports 618, input/output components 620, and an illustrativepower supply 622. Bus 610 represents what may be one or more busses(such as an address bus, data bus, or combination thereof). Although thevarious blocks of FIG. 6 are shown with lines for the sake of clarity,in reality, delineating various components is not so clear, andmetaphorically, the lines would more accurately be grey and fuzzy. Forexample, one may consider a presentation component such as a displaydevice to be an I/O component. Also, processors have memory. Werecognize that such is the nature of the art, and reiterate that thediagram of FIG. 6 is merely illustrative of an exemplary computingdevice that can be used in connection with one or more embodiments ofthe present invention. Distinction is not made between such categoriesas “workstation,” “server,” “laptop,” “hand-held device,” etc., as allare contemplated within the scope of FIG. 6 and reference to “computingdevice.”

Computing device 600 typically includes a variety of computer-readablemedia. Computer-readable media can be any available media that can beaccessed by computing device 600 and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable media may comprise computerstorage media and communication media.

Computer storage media include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can be accessed by computingdevice 600. Computer storage media excludes signals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of any ofthe above should also be included within the scope of computer-readablemedia.

Memory 612 includes computer storage media in the form of volatileand/or nonvolatile memory. The memory may be removable, non-removable,or a combination thereof. Exemplary hardware devices include solid-statememory, hard drives, optical-disc drives, etc. Computing device 600includes one or more processors that read data from various entitiessuch as memory 612 or I/O components 620. Presentation component(s) 616present data indications to a user or other device. Exemplarypresentation components include a display device, speaker, printingcomponent, vibrating component, etc.

I/O ports 618 allow computing device 600 to be logically coupled toother devices including I/O components 620, some of which may be builtin. Illustrative components include a microphone, joystick, game pad,satellite dish, scanner, printer, wireless device, etc.

Referring now to FIG. 7, FIG. 7 illustrates an exemplary distributedcomputing environment 700 in which implementations of the presentdisclosure may be employed. In particular, FIG. 7 shows a high levelarchitecture of the autonomous configuration system (“system”) in acloud computing platform 710, where the system supports seamlessmodification of software component. It should be understood that thisand other arrangements described herein are set forth only as examples.Other arrangements and elements (e.g., machines, interfaces, functions,orders, and groupings of functions, etc.) can be used in addition to orinstead of those shown, and some elements may be omitted altogether.Further, many of the elements described herein are functional entitiesthat may be implemented as discrete or distributed components or inconjunction with other components, and in any suitable combination andlocation. Various functions described herein as being performed by oneor more entities may be carried out by hardware, firmware, and/orsoftware. For instance, various functions may be carried out by aprocessor executing instructions stored in memory.

Data centers can support the distributed computing environment 700 thatincludes the cloud computing platform 710, rack 720, and node 730 (e.g.,computing devices, processing units, or blades) in rack 720. The systemcan be implemented with a cloud computing platform 710 that runs cloudservices across different data centers and geographic regions. The cloudcomputing platform 710 can implement a fabric controller 740 componentfor provisioning and managing resource allocation, deployment, upgrade,and management of cloud services. Typically, the cloud computingplatform 710 acts to store data or run service applications in adistributed manner. The cloud computing infrastructure 710 in a datacenter can be configured to host and support operation of endpoints of aparticular service application. The cloud computing infrastructure 710may be a public cloud, a private cloud, or a dedicated cloud.

The node 730 can be provisioned with a host 750 (e.g., operating systemor runtime environment) running a defined software stack on the node730. Node 730 can also be configured to perform specializedfunctionality (e.g., compute nodes or storage nodes) within the cloudcomputing platform 710. The node 730 is allocated to run one or moreportions of a service application of a tenant. A tenant can refer to acustomer utilizing resources of the cloud computing platform 710.Service application components of the cloud computing platform 710 thatsupport a particular tenant can be referred to as a tenantinfrastructure or tenancy. The terms service application, application,or service are used interchangeably herein and broadly refer to anysoftware, or portions of software, that run on top of, or access storageand compute device locations within, a datacenter.

When more than one separate service application is being supported bythe nodes 730, the nodes may be partitioned into virtual machines (e.g.,virtual machine 752 and virtual machine 754). Physical machines can alsoconcurrently run separate service applications. The virtual machines orphysical machines can be configured as individualized computingenvironments that are supported by resources 760 (e.g., hardwareresources and software resources) in the cloud computing platform 710.It is contemplated that resources can be configured for specific serviceapplications. Further, each service application may be divided intofunctional portions such that each functional portion is able to run ona separate virtual machine. In the cloud computing platform 710,multiple servers may be used to run service applications and performdata storage operations in a cluster. In particular, the servers mayperform data operations independently but exposed as a single devicereferred to as a cluster. Each server in the cluster can be implementedas a node.

Client device 780 may be linked to a service application in the cloudcomputing platform 710. The client device 780 may be any type ofcomputing device, which may correspond to computing device 700 describedwith reference to FIG. 7, for example. The client device 780 can beconfigured to issue commands to cloud computing platform 710. Inembodiments, client device 780 may communicate with service applicationsthrough a virtual Internet Protocol (IP) and load balancer or othermeans that directs communication requests to designated endpoints in thecloud computing platform 710. The components of cloud computing platform710 may communicate with each other over a network (not shown), whichmay include, without limitation, one or more local area networks (LANs)and/or wide area networks (WANs).

Having described various aspects of the distributed computingenvironment 700 and cloud computing platform 710, it is noted that anynumber of components may be employed to achieve the desiredfunctionality within the scope of the present disclosure. Although thevarious components of FIG. 7 are shown with lines for the sake ofclarity, in reality, delineating various components is not so clear, andmetaphorically, the lines may more accurately be grey or fuzzy. Further,although some components of FIG. 7 are depicted as single components,the depictions are exemplary in nature and in number and are not to beconstrued as limiting for all implementations of the present disclosure.

Embodiments described in the paragraphs below may be combined with oneor more of the specifically described alternatives. In particular, anembodiment that is claimed may contain a reference, in the alternative,to more than one other embodiment. The embodiment that is claimed mayspecify a further limitation of the subject matter claimed.

The subject matter of embodiments of the invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

For purposes of this disclosure, the word “including” has the same broadmeaning as the word “comprising,” and the word “accessing” comprises“receiving,” “referencing,” or “retrieving.” In addition, words such as“a” and “an,” unless otherwise indicated to the contrary, include theplural as well as the singular. Thus, for example, the constraint of “afeature” is satisfied where one or more features are present. Also, theterm “or” includes the conjunctive, the disjunctive, and both (a or bthus includes either a or b, as well as a and b).

For purposes of a detailed discussion above, embodiments of the presentinvention are described with reference to a distributed computingenvironment; however the distributed computing environment depictedherein is merely exemplary. Components can be configured for performingnovel aspects of embodiments, where the term “configured for” can referto “programmed to” perform particular tasks or implement particularabstract data types using code. Further, while embodiments of thepresent invention may generally refer to the autonomous configurationsystem and the schematics described herein, it is understood that thetechniques described may be extended to other implementation contexts.

Embodiments of the present invention have been described in relation toparticular embodiments which are intended in all respects to beillustrative rather than restrictive. Alternative embodiments willbecome apparent to those of ordinary skill in the art to which thepresent invention pertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects hereinabove set forthtogether with other advantages which are obvious and which are inherentto the structure.

It will be understood that certain features and sub-combinations are ofutility and may be employed without reference to other features orsub-combinations. This is contemplated by and is within the scope of theclaims.

The invention claimed is:
 1. A system for implementing autonomousconfiguration of service infrastructures, the system comprising: one ormore hardware processors and memory storing computer-executableinstructions and components embodied thereon that, when executed, by theone or more hardware processors, cause the hardware processors toexecute: a service infrastructure configuration manager to: identifydiscovered configuration data or casting configuration data for aservice infrastructure, wherein the discovered configuration data or thecasting configuration data supports the service infrastructurecircumventing a routing protocol such that the service infrastructure isalternatively configured to access remote configuration data based onthe discovered configuration data or casting configuration data, thediscovered configuration data is discovered based on an autonomousdiscovery service or the casting configuration data is identified basedon an autonomous casting service; configure an initial configurationstate in the service infrastructure, based on the discoveredconfiguration data or the casting configuration data, such that theservice infrastructure can communicate with a service providerinfrastructure associated with the service infrastructure to accessremote configuration data; access the remote configuration data from theservice provider infrastructure; and configure a final configurationstate in the service infrastructure.
 2. The system of claim 1, furthercomprising: an edge infrastructure configuration manager to: maintainrouting protocol configuration data for an edge infrastructure and aservice infrastructure, wherein the edge infrastructure configurationmanager supports the configuration of the service infrastructure basedon a routing protocol of the routing protocol configuration data,wherein a switch of the edge infrastructure configured based on therouting protocol configuration data and storing a portion of a serviceinfrastructure portion of the routing protocol configuration data, therouting protocol configuration data allows a switch of the serviceinfrastructure to communicate with the switch of the edge infrastructurebased on the routing protocol; and operate in a waiting state tofacilitate configuration of the service infrastructure, wherein thewaiting state comprises the switch of the edge infrastructure configuredbased on the routing protocol and performing waiting state operations inanticipation of configuring a link between the switch of the edgeinfrastructure configuration and the switch of service infrastructure.3. The system of claim 1, wherein the discovered configuration data isidentified from an edge infrastructure that operates in a waiting stateto configure, based on the routing protocol, the edge infrastructure tolink with an anticipated switch of the service infrastructure.
 4. Thesystem of claim 1, wherein the casting configuration data is configuredin the service infrastructure, the casting configuration data comprisesa casting IP address for the service infrastructure to peer with an edgeinfrastructure that operates in a waiting state to configure, based onthe routing protocol, the edge infrastructure to link with ananticipated switch of the service infrastructure.
 5. The system of claim4, wherein peering the service infrastructure with the edgeinfrastructure provides the service infrastructure internetaccessibility such that the service infrastructure broadcasts based onthe casting IP address to receive communications from a service providerinfrastructure.
 6. The system of claim 1, wherein the autonomousdiscovery service is a sniffing service that circumvents configurationof the service infrastructure using the routing protocol, wherein thesniffing service identifies the discovered configuration data based onmonitoring data traffic that comprises at least one reserved IP address.7. The system of claim 1, wherein the autonomous casting service is acasting service that circumvents configuration of the serviceinfrastructure using the routing protocol, wherein the casting serviceutilizes the casting configuration data to peer with an edgeinfrastructure.
 8. The system of claim 1, further comprising anintermediate provisioning manager in the service provider infrastructureto communicate intermediate remote configuration data for implementingan incremental provisioning process, wherein the intermediate remoteconfiguration data supports configuring the service infrastructure in anintermediate configuration state, the intermediate configuration stateis a trust establishing state between the service infrastructure and theservice provider infrastructure.
 9. The system of claim 1, furthercomprising a primary provisioning manager in the service providerinfrastructure to communicate primary remote configuration data forimplementing the incremental provisioning process, wherein the primaryremote configuration data supports configuring the serviceinfrastructure in a final configuration state, the final configurationstate comprising a switch of the edge infrastructure and a switch of theservice infrastructure communicating using the routing protocol whichwas previously circumvented based on the discovered configuration data.10. A computer-implemented method for providing autonomous configurationof service infrastructures, the method comprising: identifyingdiscovered configuration data for a service infrastructure, wherein thediscovered configuration data supports the service infrastructurecircumventing a routing protocol such that the service infrastructure isalternatively configured to access remote configuration data based onthe discovered configuration data, the discovered configuration data isdiscovered based on an autonomous discovery service; configuring aninitial configuration state in the service infrastructure, based on thediscovered configuration data such that the service infrastructure cancommunicate with a service provider infrastructure associated with theservice infrastructure to access remote configuration data; accessingthe remote configuration data from the service provider infrastructure;and configuring a final configuration state in the serviceinfrastructure.
 11. The method of claim 10, wherein the discoveredconfiguration data is identified from an edge infrastructure thatoperates in a waiting state to configure, based on the routing protocol,the edge infrastructure to link with an anticipated switch of theservice infrastructure.
 12. The method of claim 11, wherein the edgeinfrastructure in the waiting state performs neighbor discoveryoperations to link with the anticipated switch of the serviceinfrastructure.
 13. The method of claim 10, wherein the autonomousdiscovery service is a sniffing service, the sniffing servicecircumvents configuration of the service infrastructure using therouting protocol to identify the discovered configuration data.
 14. Themethod of claim 13, wherein the sniffing service identifies thediscovered configuration data based on monitoring data traffic thatcomprises at least one reserved IP address.
 15. The method of claim 10,wherein the sniffing service operates with the service infrastructure ina pre-configuration state comprising a switch of the serviceinfrastructure in a transparent state, the switch forwards monitoreddata traffic to a service infrastructure configuration manager.
 16. Oneor more computer storage media having computer-executable instructionsembodied thereon that, when executed, by one or more processors, causesthe one or more processors to perform a method for providing autonomousconfiguration of service infrastructures, the method comprising:identifying discovered configuration data for a service infrastructure,wherein the discovered configuration data supports the serviceinfrastructure circumventing a routing protocol such that the serviceinfrastructure is alternatively configured to access remoteconfiguration data based on the discovered configuration data, thediscovered configuration data is discovered based on an autonomousdiscovery service; configuring an initial configuration state in theservice infrastructure, based on the discovered configuration data, suchthat, the service infrastructure can communicate with a service providerinfrastructure associated with the service infrastructure to accessremote configuration data; accessing a first portion of the remoteconfiguration data from the service provider infrastructure, wherein thefirst portion of the remote configuration data is intermediate remoteconfiguration data from an intermediate provisioning manager;configuring an intermediate configuration state in the serviceinfrastructure using the intermediate remote configuration data;accessing a second portion of the remote configuration data from theservice provider infrastructure, wherein the second portion of theremote configuration data is primary remote configuration data from aprimary provisioning manager; and configuring a final configurationstate in the service infrastructure using the primary remoteconfiguration data.
 17. The media of claim 16, wherein the discoveredconfiguration data is identified from an edge infrastructure thatoperates in a waiting state to configure, based on the routing protocol,the edge infrastructure to link with an anticipated switch of theservice infrastructure, wherein the autonomous discovery service is asniffing service, the sniffing service circumvents configuration of theanticipated switch and alternatively identifies the discoveredconfiguration data based on monitoring data traffic that comprises atleast one reserved IP address.
 18. The media of claim 16, wherein thediscovered configuration data is identified from an edge infrastructurethat operates in a waiting state to configure, based on the routingprotocol, the edge infrastructure to link with an anticipated switch ofthe service infrastructure, wherein the autonomous discovery service isa casting service, the casting service circumvents configuration of theanticipated switch and alternatively identifies the discoveredconfiguration data based on monitoring data traffic that comprises acasting IP address.
 19. The media of claim 16, wherein the intermediateprovisioning manager in a service provider infrastructure operates tocommunicate intermediate remote configuration data for implementing anincremental provisioning process, wherein the intermediate remoteconfiguration data supports configuring the service infrastructure inthe intermediate configuration state, the intermediate configurationstate is a trust establishing state between the service infrastructureand the service provider infrastructure.
 20. The media of claim 16,wherein the primary provisioning manager in the service infrastructureoperates to communicate primary remote configuration data forimplementing the incremental provisioning process, wherein the primaryremote configuration data supports configuring the serviceinfrastructure in the final configuration state, the final configurationstate comprising a switch of the edge infrastructure and a switch of theservice infrastructure communicating using the routing protocol whichwas previously circumvented based on the discovered configuration data.